Skip to content

Use rctx.name if rctx.original_name is empty #1702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

mbland
Copy link
Contributor

@mbland mbland commented Feb 18, 2025

Description

Works around breakages when building under WORKSPACE with Bazel 8.1.0, as described in bazelbuild/bazel#25286. Part of #1652.

Motivation

PR #1694 added support for rctx.original_name after the implementation of bazelbuild/bazel#24467 landed in 8.1.0rc2. However, I hadn't tested WORKSPACE builds with 8.1.0rc2 before 8.1.0 came out.

This resolves the breakage until a Bazel 8 release containing a fix for bazelbuild/bazel#25286 becomes available (possibly Bazel 8.2.0).

Works around breakages when building under `WORKSPACE` with Bazel 8.1.0,
as described in bazelbuild/bazel#25286. Part of bazel-contrib#1652.

PR bazel-contrib#1694 added support for `rctx.original_name` after the implementation
of bazelbuild/bazel#24467 landed in 8.1.0rc2. However, I hadn't tested
`WORKSPACE` builds with 8.1.0rc2 before 8.1.0 came out.

This resolves the breakage until a Bazel 8 release containing a fix for
bazelbuild/bazel#25286 becomes available (possibly Bazel 8.2.0).
@mbland
Copy link
Contributor Author

mbland commented Feb 18, 2025

Thanks, @simuons! Also, it looks like a fix is out (bazelbuild/bazel#25296), and it may make it into Bazel 8.1.1 (bazelbuild/bazel#25302).

@mbland
Copy link
Contributor Author

mbland commented Feb 22, 2025

Closing this, since I can confirm that Bazel 8.1.1rc1 fixes bazelbuild/bazel#25286. Bazel 8.1.1 should be out well before we publish a version with Bazel 8 compatibility (#1652).

@mbland mbland closed this Feb 22, 2025
@mbland mbland deleted the workspace-original-name-workaround branch February 22, 2025 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants